Systems and methods for facilitating transactions using pattern recognition

ABSTRACT

Systems and methods are provided for online transactions using pattern recognition. A user of a payment provider may create and register patterns drawn by the user on a pattern entry image. The user may register the patterns by associating transaction options with each drawn pattern. Each pattern may be used to execute a particular transaction such as a purchase transaction, a payment of a specific amount, a payment to a specific recipient, or a sales transaction. When the user wishes to execute a transaction such as an online payment to a particular recipient for a particular amount, the user can redraw the registered pattern associated with payments to that recipient for that amount. A pattern can be drawn at a particular location on the pattern entry image. Different transactions can be associated with patterns drawn at different locations.

PRIORITY DATA

The present application is a continuation of U.S. patent applicationSer. No. 15/673,177, filed Aug. 9, 2017, now U.S. Pat. No. 10,068,233which is a continuation of U.S. patent application Ser. No. 14/164,051,filed Jan. 24, 2014, now U.S. Pat. No. 9,734,499, the disclosures ofwhich are hereby incorporated by reference in their entirety.

BACKGROUND Field of the Invention

The present invention generally relates to electronic commerce and, moreparticularly, to systems and methods for facilitating electroniccommerce transactions using pattern recognition.

Related Art

Computer systems and networks can facilitate the tasks of buying,selling and transferring goods and services in retail and othermarketplaces. For example, a consumer can pay for an item from either anonline merchant or at a point of sale of a brick-and-mortar storethrough the use of a payment provider that can be accessed on his or hersmart phone, tablet, laptop computer, desktop computer, or otherpersonal mobile or desktop device. In particular, users of a paymentprovider can use the payment provider website or a payment providerapplication or “app” on a mobile device to make payments to variousonline or offline merchants.

In some cases, a user of a payment provider uses the system to makerepeated payments for particular purchases such as payments to adrugstore for prescription renewals, payments for magazine, cable,internet or other subscriptions, online media purchases such as songpurchases or video purchases or other purchases.

Although many systems and methods for facilitating consumer paymentsusing a payment provider have generally worked well in the past,particularly in cases where transaction details are repeated, it wouldbe desirable to provide improved systems and methods for faster or moreconvenient payment processing for consumer transactions.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of an illustrative networked system suitablefor implementing a process for facilitating transactions using patternrecognition according to an embodiment,

FIG. 2 is a diagram of an illustrative user device having a displayshowing how a user may be provided with the ability to create a patternaccording to an embodiment.

FIG. 3 is a diagram of an illustrative user device having a displayshowing how a user may be provided with the ability to register acreated pattern by associating the pattern with a particular transactionaccording to an embodiment.

FIG. 4 is a flowchart showing an illustrative process for generatinguser transaction patterns for facilitating transactions according to anembodiment.

FIG. 5 is a diagram of an illustrative user device having a displayshowing how a user may execute a purchase and payment transaction bydrawing a previously registered pattern on the display according to anembodiment.

FIG. 6 is a flowchart showing an illustrative process for executing atransaction for a user using pattern recognition according to anembodiment.

FIG. 7 is a block diagram of an illustrative computer system suitablefor implementing one or more components in FIG. 1 according to anembodiment.

FIG. 8 is a diagram of an illustrative user device having a displayshowing how a user may execute particular transactions by drawing apreviously registered pattern at various corresponding locations on thedisplay according to an embodiment.

FIG. 9 is a flow diagram showing an illustrative process for registeringa pattern using a user-provided pattern entry image on a mobile deviceaccording to an embodiment.

FIG. 10 is a flow diagram showing an illustrative process for executinga payment action using a user-provided pattern entry image on a mobiledevice according to an embodiment.

FIG. 11 is a flowchart showing an illustrative process for executing apayment using a pattern entry image according to an embodiment.

FIG. 12 is a flowchart showing an illustrative process for sending apayment request using a pattern entry image according to an embodiment.

FIG. 13 is a flowchart showing an illustrative process for generatingand sending an invoice using a pattern entry image according to anembodiment.

FIG. 14 is a diagram of illustrative communications between a user and apayment system during pattern registration operations according to anembodiment.

FIG. 15 is a flow diagram showing another illustrative process forregistering a pattern to be used for online transactions according to anembodiment.

FIG. 16 is a diagram of illustrative communications between a user and apayment system during payment operations using a pattern entry imageaccording to an embodiment.

FIG. 17 is a flow diagram showing another illustrative process formaking a payment using a pattern entry image according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DESCRIPTION

Exemplary applications of apparatuses and methods according to thepresent invention are described in this section. These examples arebeing provided solely to add context and aid in the understanding of theinvention. It will thus be apparent to one skilled in the art that thepresent invention may be practiced without some or all of these specificdetails. In other instances, well known process steps have not beendescribed in detail in order to avoid unnecessarily obscuring thepresent invention. Other applications are possible, such that thefollowing examples should not be taken as limiting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific embodiments of the presentinvention. Although these embodiments are described in sufficient detailto enable one skilled in the art to practice the invention, it isunderstood that these examples are not limiting, such that otherembodiments may be used, and changes may be made without departing fromthe spirit and scope of the invention.

Devices, systems and methods are provided for performing activitiesrelated to online transactions such as electronic commerce transactionsusing pattern recognition. In various particular embodiments, thedevices, systems or methods can involve one or more devices incommunication over a network. Such devices, systems, and methods canfacilitate the execution of partially or completely online transactionsusing pattern recognition. According to an embodiment, drawing patternsmay be created and registered by a user with a payment provider. Eachregistered pattern may be associated with a particular electroniccommerce transaction such as a purchase transaction, a paymenttransaction, a sales transaction, an online auction transaction, orother transaction. The transaction can be executed when a user draws apreviously registered pattern using an electronic user device such as atouch screen of a smart phone or a tablet, using a mouse or touchpad ofa laptop or desktop computer, or other user input device suitable fordrawing user generated patterns.

While the various examples disclosed herein focus on particular aspectsregarding the online transactions, it will be understood that thevarious inventive principles and embodiments disclosed herein can beapplied to other types of transactions and arrangements as well. Forexample, a purchase that is performed in person using an online paymentprovider for payment may utilize one or more of the aspects and featuresfound in the various systems and methods provided.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” “an embodiment,” “various examples,”“one example,” “an example,” or “some examples” means that a particularfeature, structure, or characteristic described in connection with theembodiment or example is included in at least one embodiment. Thus,appearances of these are not necessarily all referring to the sameembodiment. Furthermore, the particular features, structures orcharacteristics may be combined in any suitable manner in one or moreembodiments.

According to an embodiment, a computer program product can comprise anon-transitory machine readable medium. The non-transitory machinereadable medium can have computer readable and executable code forinstructing one or more processors to perform any of the methodsdisclosed herein.

Beginning with FIG. 1, a block diagram is shown of a networked system100 suitable for implementing a process for facilitating a purchaseusing pattern recognition according to an embodiment. Networked system100 may comprise or implement a plurality of servers and/or softwarecomponents that operate to perform various electronic commercetransactions or processes such as payment transactions or processes.Exemplary servers may include, for example, stand-alone andenterprise-class servers operating a server OS such as a MICROSOFT® OS,a UNIX® OS, a LINUX® OS, or other suitable server-based OS. It can beappreciated that the servers illustrated in FIG. 1 may be deployed inother ways and that the operations performed and/or the servicesprovided by such servers may be combined or separated for a givenimplementation and may be performed by a greater number or fewer numberof servers. One or more servers may be operated and/or maintained by thesame or different entities.

System 100 may include a user device 110, a merchant server 140, and apayment provider server 170 in communication over a network 160. Paymentprovider server 170 may be maintained by a payment service provider,such as PayPal, Inc. of San Jose, Calif. A user 105, such as a sender orconsumer, utilizes user device 110 to perform a transaction such as anelectronic commerce transaction using payment provider server 170. Auser 105 may utilize user device 110 to initiate a payment transaction,receive a transaction approval request, or reply to the request. Notethat transaction, as used herein, refers to any suitable actionperformed using the user device, including payments, transfer ofinformation, display of information, purchases, sales, online listings,etc. For example, user 105 may utilize user device 110 to initiate adeposit into a savings account. Although only one merchant server isshown, a plurality of merchant servers may be utilized if the user ispurchasing products or services from multiple merchants.

User device 110, merchant server 140, and payment provider server 170may each include one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 100, and/or accessible over network 160.

Network 160 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 160 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks.

User device 110 may be implemented using any appropriate hardware andsoftware configured for wired and/or wireless communication over network160. For example, in one embodiment, user device 110 may be implementedas a personal computer (PC), a smart phone, personal digital assistant(PDA), laptop computer, and/or other types of computing devices capableof transmitting and/or receiving data, such as an iPad™ from Apple™.

User device 110 may include one or more browser applications 115 whichmay be used, for example, to provide a convenient interface to permituser 105 to browse information available over network 160. For example,in one embodiment, browser application 115 may be implemented as a webbrowser configured to view information available over the Internet, suchas a user account for setting up a shopping list and/or merchant sitesfor viewing and purchasing products and services. User device 110 mayalso include one or more toolbar applications 120 which may be used, forexample, to provide client-side processing for performing desired tasksin response to operations selected by user 105. In one embodiment,toolbar application 120 may display a user interface in connection withbrowser application 115.

User device 110 may further include other applications 125 as may bedesired in particular embodiments to provide desired features to userdevice 110. For example, other applications 125 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 160, or othertypes of applications.

Applications 125 may also include email, texting, voice and IMapplications that allow user 105 to send and receive emails, calls, andtexts through network 160, as well as applications that enable the userto communicate, transfer information, make payments, and otherwiseutilize a smart wallet through the payment provider as discussed above.User device 110 may include one or more user identifiers 130 which maybe implemented, for example, as operating system registry entries,cookies associated with browser application 115, identifiers associatedwith hardware of user device 110, or other appropriate identifiers, suchas used for payment/user/device authentication. In one embodiment, useridentifier 130 may be used by a payment service provider to associateuser 105 with a particular account maintained by the payment provider. Acommunications application 122, with associated interfaces, enables userdevice 110 to communicate within system 100.

User device 110 also may include components and applications thatmonitor and/or detect user-drawn patterns. For example, user device 110may include a touch screen that displays information to user 105 andreceives user input from user 105. User device 110 may monitor userinput on the touch screen, on any other touch-sensitive device (e.g., atouchpad on a laptop), or using other input components (e.g., a mouse)and may recognize user generated patterns for storage, for associationwith transactions, and/or to activate certain functions (e.g., purchasetransactions, payment transactions, sales transactions, and listingtransactions). In one embodiment, user device 110 may include a cameraconfigured to accept user inputs such as user-drawn patterns from user105. In still another embodiment, user device 110 may include a motiondetector, (e.g., a gyroscope), for detecting the motion of user device110 itself. User device 110 may monitor the movement of user device 110for input of any predetermined patterns made by user 105 that activatetransactions.

User derive 110 also may collect location data using Global PositioningSystem (GPS) circuitry to identify a location of user device 110. Othermeans for collecting location data., such as WiFi devices, Near-FieldCommunication (NFC) devices, or the like also may be included in userdevice 110 for determining a location of user device 110. Thus, userdevice 110 may determine a current location of user device 110 based onthe collected location data. In another embodiment, user device 110 maysend the location data to payment provider server 170 and paymentprovider server 170 may determine a current location of user device 110based on the location data.

Merchant server 140 may be maintained, for example, by a merchant orseller offering various products and/or services. The merchant may havea physical point-of-sale (POS) store front. The merchant may be aparticipating merchant who has a merchant account with the paymentservice provider. Merchant server 140 may be used for POS or onlinepurchases and transactions. Generally, merchant server 140 may bemaintained by anyone or any entity that receives money, which includescharities as well as banks and retailers. For example, a payment may bea donation to charity or a deposit to a bank account such as a savingsaccount.

Merchant server 140 may include a database 145 identifying availableproducts (including digital goods) and/or services (e.g., collectivelyreferred to as items) which may be made available for viewing andpurchase by user 105. Accordingly, merchant server 140 also may includea marketplace application 150 which may be configured to serveinformation over network 160 to browser 115 of user device 110. In oneembodiment, user 105 may interact with marketplace application 150through browser applications over network 160 in order to view variousproducts, food items, or services identified in database 145.

Merchant server 140 also may include a checkout application 155 whichmay be configured to facilitate the purchase by user 105 of goods orservices online or at a physical POS or store front. Checkoutapplication 155 may be configured to accept payment information from oron behalf of user 105 through payment service provider server 170 overnetwork 160. For example, checkout application 155 may receive andprocess a payment confirmation from payment service provider server 170,as well as transmit transaction information to the payment provider andreceive information from the payment provider (e.g., a transaction ID).Checkout application 155 may be configured to receive payment via aplurality of payment methods including cash, credit cards, debit cards,checks, money orders, or the like.

Payment provider server 170 may be maintained, for example, by an onlinepayment service provider which may provide payment between user 105 andthe operator of merchant server 140. In this regard, payment providerserver 170 includes one or more payment applications 175 which may beconfigured to interact with user device 110 and/or merchant server 140over network 160 to facilitate the purchase of goods or services,communicate/display information, and send payments by user 105 of userdevice 110.

Payment provider server 170 also maintains a plurality of user accounts180, each of which may include account information 185 associated withconsumers, merchants, and funding sources, such as banks or credit cardcompanies. For example, account information 185 may include privatefinancial information of users of devices such as account numbers,passwords, device identifiers, user names, phone numbers, credit cardinformation, bank information, or other financial information which maybe used to facilitate online transactions by user 105. Accountinformation may also include stored patterns that are associated withparticular transactions such as payments (e.g., payments of a particulardollar amount) that may trigger the transactions when a matching patternis provided by a user. The matching pattern may be provided by the userby drawing the pattern on a touch screen or a touchpad of user device110, a movement of user device 110, or a gesture of user 105 captured bya camera of user device 110. Payment application 175 may be configuredto interact with merchant server 140 on behalf of user 105 during atransaction with checkout application 155 to track and manage purchasesmade by users and which and when funding sources are used. Paymentapplication 175 may be configured to determine the existence of and tomanage accounts for user 105, as well as create new accounts ifnecessary. Payment application 175 may be configured to execute one ormore payment transactions in response to receiving and recognizing adrawn pattern from user 105.

A transaction processing application 190, which may be part of paymentapplication 175 or may be separate from application 175, may beconfigured to receive information from user device 110 and/or merchantserver 140 for processing and storage in a payment database 195.Transaction processing application 190 may include one or moreapplications for processing information from user 105 for processing anorder and for payment using various selected funding instruments,including operations for initial purchase and for payment after purchaseas described herein. As such, transaction processing application 190 maystore details of an order from individual users, including a fundingsource used, available credit options, etc. Transaction processingapplication 190 may be configured to execute one or more transactionssuch as electronic commerce transactions in response to receiving andrecognizing a drawn pattern from user 105.

One or more of merchant server 140, payment provider server 170, anduser device 110 may be used to execute any suitable transaction inresponse to receiving and recognizing a drawn pattern from a user. Asexamples, in response to receiving and recognizing a drawn pattern anyor all of merchant server 140, payment provider server 170, and userdevice 110 may execute a payment of a particular dollar amount from aparticular funding source to a particular merchant, may list for sale aproduct at a particular price for a particular time period on a merchantwebsite, may initiate delivery of a purchased item from a seller, mayaccept an offer from a potential buyer, may alter details of a currentlylisted product for sale, or may execute any other suitable transactionperformed partially or completely online.

In one particular situation that is sometimes discussed herein as anexample, a user may input a predetermined or pre-registered pattern touser device 110 that is provided to payment provider server 170 andthat, when recognized by server 170, executes, for example, a payment toa particular merchant, of a particular amount, from a particular fundingsource. The particular merchant, the particular amount, and theparticular funding source may have been previously associated with therecognized pattern during pattern registration operations performed bythe user.

FIG. 2 shows an example of a user device having a display that isperforming pattern registration operations in cooperation with, forexample, a payment provider server in accordance with an embodiment. Asshown in FIG. 2, a user device 110 may have a display 200 such astouchscreen display. During pattern registration operations, the displaymay be instructed (e.g., by a payment provider app or payment providerwebsite) to display an image such as pattern entry image 202 that can beused for pattern entry by a user. In the example of FIG. 2, image 202 isan N by M matrix of dots 204. However, this is merely illustrative. Ifdesired, any suitable image such as a user-provided image (e.g., adigital photograph that has been uploaded by the user) may be providedon display 200 for pattern entry.

During pattern registration operations, the user may draw one or morepatterns such as pattern P1 or pattern P2 (as examples) on the image202. The image 202 may be used to facilitate the drawing of the patternby the user (e.g., by providing a visual guide for the user's finger)and may also facilitate the drawing of more easily recognized patternsfor later recognition by, for example, a payment provider. The exampleof FIG. 2 shows an N=4 by M=5 dot matrix. However, this is merelyillustrative. It should be appreciated that a matrix having any numbersN and M of respective rows and columns of dots may be provided or anyother image may be provided. In one embodiment, the user may be providedwith the ability to choose the numbers N and M of respective rows andcolumns of dots to be provided in the pattern entry image.

Once a particular pattern (e.g., pattern PI, pattern P2, a discontinuouspattern that includes both patterns P1 and P2, or any other continuousor discontinuous pattern) has been drawn by the user, the pattern may besaved (e.g., using memory or other storage on user device 110 or paymentprovider sever 170) and the user may be prompted to associate that savedpattern with a particular transaction such as an electronic commercetransaction.

The location of the drawn pattern on the pattern entry image 202 mayalso be stored so that the same pattern drawn in different locations onthe image can be associated with different transactions (e.g., paymentsof different amounts) or so that a pattern entered at the wrong positionon the image can be blocked from authorizing the transaction.

FIG. 3 shows an example of a user device having a display that isperforming pattern registration operations in cooperation with, forexample, a payment provider server in accordance with an embodiment. Asshown in FIG. 3, display 200 may provide a user with an indicator 300that indicates that a drawn pattern has been successfully saved. Inaddition to indicator 300, the user may be provided with one or morepattern association options 302 that can be associated with the savedpattern.

Pattern association options 302 may include a transaction type option304, a currency amount option 306, a sell listing option 308, amerchant/recipient option 310, a funding source option 312, and/or othersuitable transaction options that can be associated with a pattern.Transaction type option 304 may include an option to associate aparticular saved pattern with an electronic commerce transaction (e.g.,a purchase transaction, a sales transaction, a payment transaction, apayment request transaction, an invoicing transaction, or other onlinefinancial transaction) or another type of transaction. Currency amountoption 306 may include an option for determining a payment amount, aselling price, a minimum selling price, a purchase price range, or otherprice-related options to be associated with the saved pattern. Currencyamount option. 306 may be specified in dollars, euros, or any othersuitable currency. Sell listing options 308 may include options forlisting items for sale on, for example, an auction website. Listingoption 308 may include options for immediately listing a particularitem, an auction end time option for an item, a standard descriptionoption for an item, a number of items option for a listing, or otherlisting options that can be associated with a saved pattern.Merchant/recipient option 310 may include an option to associate aparticular saved pattern with a particular merchant or any otherparticular recipient. Recipients of payments, payment requests, and orinvoices (as examples) may be identified by a recipient account at thepayment provider or by other identifying information such as an emailaddress or a telephone number at which the recipient can receivepayments, instructions for receiving payments, payment requests, and/orinvoices (as examples). A recipient may be a recipient of a payment or apayer that receives payment requests and/or invoices according to someembodiments.

Each saved pattern can be associated with one or more non-conflictingoptions from options 302 that specify transaction details for aparticular transaction. In various embodiments, a pattern may be used tomake a payment of a specific amount to any recipient or a payment of anyamount to a specific recipient. For example, a particular pattern mayalways be used to make payments of $100. In another example, aparticular pattern may be used to make payments to a friend at aparticular email address. In another embodiment, a pattern such aspattern P1 of FIG. 2 may be associated with a transaction for payment ofan amount such as $100 to a seller from whom the user has purchased aproduct (e.g., in an online auction website such as an eBay, Inc.website, or another merchant website) from a particular funding sourceof the user that is associated with a stored user account. As anotherexample, a pattern such as pattern P2 of FIG. 2 may be associated with atransaction of listing an item that is currently displayed on the userdevice display in a 10-day online auction with a minimum selling priceof $102 and with an option to receive payment through a particularpayment provider such as PayPal, Inc. of San Jose, Calif. It should beappreciated that these examples and embodiments are merely illustrative.

In various embodiments, any suitable pattern that can be drawn by a usercan be associated with any suitable transaction. In various embodiments,options 302 can be provided to a user on a webpage associated with apayment provider server, on a app that communicates with a paymentprovider server, or on an app that resides completely on a user device(as examples). Saved patterns and associated transaction options can bestored on the user device, on the payment server, or elsewhere in anonline transaction system.

In one embodiment, the pattern to be saved can be entered after thepattern association options have been selected. For example, a user mayexecute a transaction such as a payment without using any patternrecognition operations and, following that transaction, the user can beprovided with the option to create a pattern to associate with thattransaction. In some embodiments, a payment provider can provide theuser with the option to create a pattern after detecting that the userhas repeatedly (e.g., more than once, more than twice, more than threetimes, etc.) executed the same transaction (e.g., a payment of the sameamount from the same funding source to the same merchant).

FIG. 4 is a flowchart showing illustrative operations in a process forcreating and registering a pattern according to one embodiment.

At step 400, user log-in information such as a username and a passwordmay be received (e.g., at a payment provider server from a user device).

At step 402, a pattern entry image of the type shown in FIG. 2 may beprovided to a user. The pattern entry image may be provided by, forexample, a payment provider server 170. The pattern entry image may bedisplayed to the user on a user device display. As described herein, thepattern entry image may be a grid (matrix) of N×M dots, a user-providedimage, or any other suitable image on which a pattern can be drawn.

At step 404, pattern entry data may be received (e.g., from a userentering a pattern on a user device). The pattern entry data may betouchscreen data generated by a user drawing a pattern on a touchscreenof the user device over the pattern entry image according to anembodiment. According to other embodiments, the pattern entry data maybe mouse-generated data generated by a user drawing a pattern by movinga cursor that is displayed on a touch or non-touch display over thepattern entry image.

At step 406, the received pattern entry data may be stored (e.g., usingmemory associated with the user device or memory associated with thepayment provider server).

At step 408, pattern association options of the type shown in FIG. 3 maybe provided to the user. As described above in connection with FIG. 3,pattern association options may include transaction type options,currency amount options such as price options, listing options,merchant/recipient options, or other transaction options.

At step 410, pattern association selections may be received (e.g., fromthe user device). Receiving the pattern association selections mayinclude receiving user-selected ones of the provided pattern associationoptions that specify a set of transaction details from the user to beassociated with the pattern. The set of transaction details may definean action such as an electronic commerce transaction to be performedwhen the pattern is later received by the payment provider. For example,a payment provider server may receive data (e.g., tapped touchscreendata or typed real or virtual keyboard data) that indicates that a userhas selected a set of transaction details for a particular type offuture transaction (e.g., an action resulting in a payment in the amountof $60 to a grocery store merchant from a bank account).

At step 412, a pattern confirmation prompt may he provided. The patternconfirmation prompt may include an option for a user to confirm theassociation of the pattern association selections with the pattern.

At step 414, a pattern confirmation may he received (e.g., from the userdevice).

At step 416, the pattern association selections may he stored inassociation with the stored pattern entry data (e.g., on memory of apayment provider server, memory of a user device or other hardwarememory system storage). In this way, a user may register a pattern bysaving the pattern and storing specific transaction actions to be takenwhen the user later enters the pattern again.

In general, the steps described above in connection with FIG. 4 may heperformed in any suitable order and/or combined in any suitable way forcreating and registering patterns to be used in transaction operationsinvolving pattern recognition,

Stored patterns that have been registered can be used by the user tomake payments, to purchase items for sale, to sell items, or to performother transactions.

In various embodiments, user may utilize pre-registered patterns toexecute various transactions such as payments, requests for payment,invoice generation, product purchase and/or item listing (as examples).

FIG. 5 shows an example of a user device having a display that isperforming product purchase and item listing transactions in response touser-drawn patterns in cooperation with, for example, a payment providerserver in accordance with an embodiment. As shown in FIG. 5, display 200may be used to provide a user with an item for sale 500 and/or an itemto be sold 502. An item for sale 500 may be listed, for example, on amerchant webpage. Item for sale 500 may include information about theitem such as an image 504 of the item, a purchase price 506 for theitem, and/or item details 508 (e.g., text or image descriptions of itemspecifications and/or seller details). Item to be sold 502 may includeidentifying information that has been provided by the user or by aprevious seller such as an image 510 of the item and item details 512.

As shown in FIG. 5, a user may use an entry device such as the user'sfinger 514 to draw a pattern PA on the display 200 (e.g., a touchscreendisplay) or may draw the pattern PA using another device (e.g., amouse). The pattern PA may he drawn partially or completely over theitem for sale or the pattern PA may be drawn elsewhere on the display.In some embodiments, the success, failure, or type of transaction thatis performed in response to a drawn pattern may depend on the locationon the display at which the pattern was drawn. The pattern PA may be apre-registered pattern that the user has already stored with options topurchase an item for the price from the seller using a particularfunding source (e.g., a credit card or a payment account with a paymentprovider) according to an embodiment. The user may thereby automaticallypurchase the item for sale 500 by drawing the pattern PA over the itemfor sale according to an embodiment,

As another example, a user may use an entry device such as the user'sfinger 514 or a mouse to draw another pattern such as pattern PB on thedisplay 200 to sell an item such as item to be sold 502. The pattern PBmay be drawn partially or completely over the item to be sold or thepattern PB may be drawn elsewhere on the display. The pattern PB may bea pre-registered pattern that the user has already stored with optionsto list an item for sale for a predetermined price or price range on aparticular merchant server with particular payment acceptance method(for example). The user may thereby automatically list the item to besold 502 by drawing the pattern PB over the item to be listed accordingto an embodiment.

Although the user device 110 of FIG. 5 is shown to be the same devicethat was used to enter and register the pattern, it should be appreciatethat this is merely illustrative. In accordance with variousembodiments, the user device that is used to create and registerpatterns can be the same or different from a user device that is used toexecute transactions using the patterns.

In the example of FIG. 5, patterns PA and PB are entered without thepresentation to the user of the pattern entry image that was used whenregistering the respective patterns. However, this is merelyillustrative. In some embodiments, the pattern entry image may beprovided to the user so that the user can enter the pattern at theappropriate location on the image for execution of a transaction.

FIG. 6 is a flowchart showing a process for executing transactions suchas electronic commerce transactions using pattern recognition accordingto an embodiment.

At step 600, user log-in information such as a username and a passwordmay be received (e.g., at a payment provider server from a user device).

At step 602, transaction options may he provided to a user. Thetransaction options may be items for sale, items to be listed for sale,payment options, payment request options, invoicing options, or otherelectronic commerce transaction options (as examples). The transactionoptions can be provided on a merchant website, on an auction website, orin a user application running on a user device. In some embodiments,step 602 may be omitted if the user has registered patterns that specifyall of the necessary information for executing a transaction.

At step 604, a pattern entry image may he provided. The pattern entryimage may be a pattern entry image that was provided to the user whenthe user registered one or more patterns. The pattern entry image may,if desired, be selected by the user from multiple pattern entry images.

At step 606, a pattern entry may he obtained. Obtaining a pattern entrymay include receiving touchscreen data generated by a user when the userdraws a pattern on the provided pattern entry image using a touchscreenof a user device. However, this is merely illustrative. The patternentry may be obtained by any means through which a user can draw apattern. In another example, the user may move a mouse or other devicein a way that generates data representing a user-drawn pattern on aprovided pattern entry image.

At step 608, the entered pattern may be recognized (e.g., by the paymentprocessor server or by the user device). Recognizing the pattern mayinclude mapping received pattern entry data such as touchscreen data toa data format that matches the format in which previously registeredpatterns have been stored, comparing the entered pattern to one or morepreviously registered patterns, and matching the entered pattern to apreviously registered pattern based on the comparison according tovarious embodiments.

At step 610, the location of the entered pattern may be determined.Determining the location of the entered pattern may include determiningthe location on the pattern entry image and/or the location on thetouchscreen display at which the pattern was entered.

At step 612, stored pattern association selections that are associatedwith the recognized pattern may be obtained (e.g., from storage such asmemory associated with a payment provider server or a user device onwhich the pattern association selections have been stored in associationwith registered, saved patterns). The pattern association selections maybe, for example, pattern association selections of the type describedherein in connection with FIG. 3.

At step 614, a confirmation prompt may optionally be provided thatallows the user to confirm or cancel a transaction associated with therecognized pattern, the determined location, and the stored patternassociation selections.

At step 616, location-dependent amount change information and/or aconfirmation may be received. In one embodiment, the user may tapvarious locations on a touchscreen to adjust the amount of a paymentassociated with a recognized pattern (e.g., by tapping a top portion ofthe display to increment amount by, for example, $5 or by tapping on abottom portion of the display to decrease amount by for example, $5). Inanother embodiment, a confirmation of the transaction may be receivedwithout any location-dependent amount change information. In anotherembodiment, the transaction may be executed without an additionalconfirmation or any location-dependent amount change information.

At step 618, a transaction may be completed by taking suitable actionbased on the obtained pattern association selections, the location ofthe entered pattern, and/or the location-dependent amount changeinformation. Suitable action may include sending payment of an amount toa merchant or a recipient from a funding source as determined by thepattern association selections, listing an item for sale as determinedby the pattern association selections, requesting a payment asdetermined by the pattern association selections, or performing otheroperations for transactions defined by the obtained pattern associationselections. In this way, a user can perform a particular onlinetransaction such as making a payment by providing a particularassociated pattern.

In general, the steps described above in connection with FIG. 6 may beperformed in any suitable order and/or combined in any suitable way forexecuting transaction operations involving pattern recognition.

FIG. 7 is a block diagram of a computer system 700 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the user device may comprise a personalcomputing device (e.g., smart phone, a computing tablet, a personalcomputer, laptop, PDA, Bluetooth device, key FOB, badge, etc.) capableof communicating with the network. The merchant and/or payment providermay utilize a network computing device (e.g., a network server) capableof communicating with the network. It should be appreciated that each ofthe devices utilized by users, merchants, and payment providers may beimplemented as computer system 700 in a manner as follows.

Computer system 700 includes a bus 702 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 700. Components include aninput/output (I/O) component 704 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons orlinks, etc., and sends a corresponding signal to bus 702. I/O component704 may also include an output component, such as a display 711 and acursor control 713 (such as a keyboard, keypad, mouse, etc.). Anoptional audio input/output component 705 may also be included to allowa user to use voice for inputting information by converting audiosignals. Audio I/O component 705 may allow the user to hear audio. Atransceiver or network interface 706 transmits and receives signalsbetween computer system 700 and other devices, such as another userdevice, a merchant server, or a payment provider server via network 160.In one embodiment, the transmission is wireless, although othertransmission mediums and methods may also be suitable. A processor 712,which can be a micro-controller, digital signal processor (DSP), orother processing component, processes these various signals, such as fordisplay on computer system 700 or transmission to other devices via acommunication link 718. Processor 712 may also control transmission ofinformation, such as cookies or IP addresses, to other devices.

Components of computer system 700 also include a system memory component714 (e.g., RAM), a static storage component 716 (e.g., ROM), and/or adisk drive 717. Computer system 700 performs specific operations byprocessor 712 and other components by executing one or more sequences ofinstructions contained in system memory component 714. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 712 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 714, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 702. In oneembodiment, the logic is encoded in non--transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 700. In various other embodiments of thepresent disclosure, a plurality of computer systems 700 coupled bycommunication link 718 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

As described herein, action associated with a particular registeredpattern may depend on the location at which that pattern is entered.FIG. 8 is a diagram of a user device 110 showing how a particularpattern P may be entered at various locations such as locations L1, L2,and/or L3 on a pattern input image 202. Pattern P may be apre-registered pattern. In one embodiment, a pattern P drawn by the useron display 200 at location L1 may execute a payment of $100 to arecipient, a pattern P drawn by the user on display 200 at location L2may execute a payment of $50 to the recipient, and a pattern P drawn bythe user on display 200 at location L3 may execute a payment of $20 tothe recipient. However, this is merely illustrative. In variousembodiments, any suitable pattern at any suitable location can beassociated with any suitable transaction.

FIG. 9 is a flow diagram showing how a user may register patterns atspecific locations on a pattern entry image for association with apayment transaction in accordance with an embodiment. As shown in FIG.9, a user may choose a pattern entry image such as image 900, draw oneor more patterns such as patterns P′ and P″ on the image at respectivelocations LA and LB, enter payment operation details (e.g., patternassociation selections), and save the pattern. Patterns P′ and P″ may beindividual patterns to be registered or may be portions of onediscontinuous pattern to be registered.

As shown in FIG. 9, pattern association options 302 may be provided on adisplay 200 of a user device 110 that is implemented as a smart phonesuch as an iPhone® of Apple, Inc. Options 302 such as merchant/recipientoption 310, currency amount option 306, currency type option 902,transaction type option 304, and additional comments option 904 may beprovided in a pattern registration app. As shown, options 302 may beprovided as text entry options (e.g., options 310, 306, and 904) and/ordrop-down menu options (e.g., options 304 and 902). In some embodiments,additional options such as save option 906 for saving patternassociation selections and cancel option 908 for canceling patternregistration may also be provided. In some embodiments, a patternregistration confirmation page 910 may be provided having a confirmationoption 914 that can be selected by the user to confirm the patternregistration. Pattern association selections such as selections 912 maybe provided to the user for confirmation. Once a pattern has beenregistered, the user can later use a pattern drawing application toexecute a transaction such as a payment.

FIG. 10 is a flow diagram showing how a user may execute a payment bydrawing previously registered patterns P′ and P″ on pattern entry image900. As shown, the user may open a draw pattern tab in, for example, apayment provider application on a smartphone, be provided with patternentry image 900, and draw patterns P′ and P″ at the appropriatelocations on pattern entry image 900, thereby executing a payment asdetermined by selections 912 of FIG. 9. After payment execution, theuser may be provided with a confirmation screen 1000 on which details1002 matching options 912 are provided.

FIGS. 11, 12, and 13 are flowcharts showing illustrative processes forexecuting respectively a payment, a payment request, and an invoicetransaction by entering a pre-registered pattern on a provided patternentry image.

Referring now to FIG. 11, a process for executing a payment is shown.

At step 1102, user log-in information such as a username and a passwordmay be received (e.g., at the payment provider server from a userdevice).

At step 1104, a pattern entry image that was previously used whenregistering one or more patterns may be provided to the user.

At step 1106, a pattern entry may be received from the user. The patternentry may be received when the user draws a pre-registered pattern onthe provided pattern entry image at, for example, a particular location.

At step 1108, in response to receiving the pattern entry, a payment maybe sent to a recipient as determined by the pre-registered pattern.

Referring now to FIG. 12, a process for executing a payment request isshown.

At step 1202, user log-in information such as a username and a passwordmay be received (e.g., at the payment provider server from a userdevice).

At step 1204, a pattern entry image that was previously used whenregistering one or more patterns may be provided to the user.

At step 1206, a pattern entry may be received from the user. The patternentry may be received when the user draws a pre-registered pattern onthe provided pattern entry image at, for example, a particular location.

At step 1208, in response to receiving the pattern entry, a paymentrequest may be sent to a recipient as determined by the pre-registeredpattern.

Referring now to FIG. 13, a process for generating and sending aninvoice is shown.

At step 1302, user log-in information such as a username and a passwordmay be received (e.g., at the payment provider server from a userdevice).

At step 1304, a pattern entry image that was previously used whenregistering one or more patterns may be provided to the user.

At step 1306, a pattern entry may be received from the user. The patternentry may be received when the user draws a pre-registered pattern onthe provided pattern entry image at, for example, a particular location.

At step 1308, in response to receiving the pattern entry data, aninvoice may be generated as determined by the pre-registered pattern.

At step 1310, the invoice may be sent to a recipient as determined bythe pre-registered pattern.

FIG. 14 is a diagram of illustrative communications between a user and apayment system during pattern registration operations according to anembodiment. As shown in FIG. 14 a user 1400 (e.g., a user operating userdevice 110) may exchange communications with a payment system 1402(e.g., payment provider server 170). For example, user 1400 and paymentsystem 1402 may exchange authorization information such as log-ininformation 1404 when a user sends log-in credentials to the paymentsystem and the payment system notifies that user that they arelogged-in.

The user 1400 and payment system 1402 may also exchange patternregistration information 1406 when the user instructs the payment systemto open a pattern page for entering a pattern, chooses an image or a dotmatrix option for a pattern entry image, draws a pattern (e.g., on thepattern entry image), associates the drawn pattern with a “Send Payment”action (as an example), and saves the pattern. When the user instructsthe payment system to save the pattern, the payment system may generateinternal communications 1408 for saving the pattern.

FIG. 15 is a flow diagram showing a method of use during which thecommunications of FIG. 14 may be exchanged according to an embodiment.As shown in FIG. 15, at block 1502, a user may execute a mobile ortablet application (as examples) log in to a payment system with a userdevice.

At block 1504, the user may open a pattern page such as a pattern entrypage on the user device.

At block 1506, the user may select a dot-matrix or a user-provided imageoption.

At block 1508, if the user selects a dot-matrix option,the user maydefine the parameters (e.g., the numbers N and M of rows and columns ofdots) for the dot matrix pattern entry image.

At block 1510, if the user selects the user-provided image option, theuser may choose a pattern entry image.

At block 1512, the user may draw a pattern on the pattern entry image.

At block 1514, the user may associate the drawn pattern with an actionsuch as a send payment operation with particular payment details to beperformed.

At block 1515, the user may review the payment details for the sendpayment operations.

At block 1516, the user may confirm the payment details. The registeredpattern (e.g., the pattern and the payment details) may then be storedon a database 1520 (e.g., memory of the payment provider server).

FIG. 16 is a diagram of illustrative communications between a user and apayment system during a payment transaction using a pre-registeredpattern according to an embodiment. As shown in FIG. 16, a user 1600(e.g., a user operating user device 110) may exchange communicationswith a payment system 1602 (e.g., payment provider server 170). Forexample, user 1600 and payment system 1602 may exchange authorizationinformation such as log-in information 1604 when a user sends log-incredentials to the payment system and the payment system notifies thatuser that they are logged-in.

The user 1600 and payment system 1602 may also exchange paymentexecution information 1606 when the user instructs the payment system toopen a pattern page for entering a pattern, the payment system sends apattern image list of possible pattern entry images, the user chooses aselected one of the pattern entry images and draws a pre-registeredpattern, and the payment system sends a success or error message. Whenthe user opens the pattern page, the payment system may generateinternal communications 1605 to obtain (get) any pattern entry images(pattern images) associated with the user from storage such as adatabase. When the user chooses the image and draws the pre-registeredpattern, the payment system may generate internal communications 1620 toinitiate a payment process and transfer money as determined by thepre-registered pattern.

FIG. 17 is a flow diagram showing a method of use during which thecommunications of FIG. 16 may be exchanged according to an embodiment.As shown in FIG. 17, at block 1702, a user may execute a mobile ortablet application (as examples) log in to a payment system.

At block 1704, the user may open a pattern page such as a pattern entrypage on the user device.

At block 1706, the user may choose a pattern entry image. The patternentry image may be chosen when a payment system gets (obtains) patternentry images from a database 1700 (e.g., a database of a paymentprovider server) and provides a pattern entry images list (patternimages list) to the user.

At block 1708, the user may draw a pattern on the pattern entry image.

At block 1710, the payment system may perform pattern matchingoperations as described herein by obtaining (getting) one or moredrawing patterns from database 1700 and receiving a list of possibledrawing patterns (e.g., drawing patterns to be compared with the drawnpattern of block 1708) from database 1700.

At block 1712, the payment system may transfer money for a paymentassociated with the drawn pattern of block 1708.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

1. (canceled)
 2. A system, comprising: one or more processors, one ormore computer-readable memories, with program instructions stored on theone or more computer-readable memories, the one or more processorsconfigured to execute the program instructions to cause the system toperform the operations comprising: detecting an input by a user providedvia a touchscreen of a computing device, the input comprising a firstdrawing corresponding to a first image displayed on the touchscreen anda second drawing corresponding to a second image displayed on thetouchscreen, the first drawing being different from the second drawing;and in response to the detecting the input by the user on thetouchscreen, causing a first process and a second process to beperformed by the computing device, the first process corresponding to afirst entity associated with the first image and the second processcorresponding to a second entity associated with the second image. 3.The system of claim 2, wherein the first drawing is located in a firstarea of the touchscreen that corresponds to the first image.
 4. Thesystem of claim 2, wherein the first drawing is located at leastpartially on the first image.
 5. The system of claim 3, wherein thecausing the first process to be performed by the computing device is inresponse to determining that the first drawing is in the first area ofthe touchscreen.
 6. The system of claim 2, wherein the first process isperformed by a first application on the computing device and the secondprocess is performed by a second application on the computing device. 7.The system of claim 2, wherein the first process and the second processare performed by a first application on the computing device.
 8. Thesystem of claim 2, wherein the first process includes performing atransaction with the first entity, and wherein the first drawingcorresponds to an information associated with the transaction.
 9. Amethod comprising: detecting an input by a user provided via atouchscreen of a computing device, the input comprising a first drawingcorresponding to a first image displayed on the touchscreen and a seconddrawing corresponding to a second image displayed on the touchscreen,the first drawing being different from the second drawing; and inresponse to the detecting the input by the user on the touchscreen,causing a first process and a second process to be performed by thecomputing device, the first process corresponding to a first entityassociated with the first image and the second process corresponding toa second entity associated with the second image.
 10. The method ofclaim 9, wherein the first drawing is located in a first area of thetouchscreen that corresponds to the first image.
 11. The method of claim9, wherein the first drawing is located at least partially on the firstimage.
 12. The method of claim 10, wherein the causing the first processto be performed by the computing device is in response to determiningthat the first drawing is in the first area of the touchscreen.
 13. Themethod of claim 9, wherein the first process is performed by a firstapplication on the computing device and the second process is performedby a second application on the computing device.
 14. The method of claim9, wherein the first process and the second process are performed by afirst application on the computing device.
 15. The method of claim 9,wherein the first process includes performing a transaction with thefirst entity, and wherein the first drawing corresponds to aninformation associated with the transaction.
 16. A computer programproduct comprising: one or more computer-readable tangible storagedevices, and program instructions stored on at least one of the one ormore storage devices, the program instructions when executed cause amachine to perform operations comprising: detecting an input by a userprovided via a touchscreen of a computing device, the input comprising afirst drawing corresponding to a first image displayed on thetouchscreen and a second drawing corresponding to a second imagedisplayed on the touchscreen, the first drawing being different from thesecond drawing; and in response to the detecting the input by the useron the touchscreen, causing a first process and a second process to beperformed by the computing device, the first process corresponding to afirst entity associated with the first image and the second processcorresponding to a second entity associated with the second image. 17.The computer program product of claim 16, wherein the first drawing islocated at least partially on the first image.
 18. The computer programproduct of claim 17, wherein the causing the first process to beperformed by the computing device is in response to determining that thefirst drawing is in a first area of the touchscreen that corresponds tothe first image.
 19. The computer program product of claim 16, whereinthe first process is performed by a first application on the computingdevice and the second process is performed by a second application onthe computing device.
 20. The computer program product of claim 16,wherein the first process and the second process are performed by afirst application on the computing device.
 21. The computer programproduct of claim 16, wherein the first process includes performing atransaction with the first entity, and wherein the first drawingcorresponds to an information associated with the transaction.